The Requirements Management Plan has to be in line with the ambition of the client regarding the requirements. The Requirements Management Plan is first created and then approved by the client and added to the guidelines of the engagement. It will not be mentioned as an input during the activities and tasks of the As-Is Understanding.

As stated in Rational Unified Process (RUP): The purpose of the Requirements Management Plan is to describe how the engagement will set up and manage the requirement artifacts, associated requirement types, and their respective requirement attributes. The plan also addresses how traceability will be managed.

The operational guidelines in the Requirements Management Plan describe for the engagement:

• which deliverables are related (traceability);
• the types of requirements and their relation (hierarchy);
• the attributes of the requirements and their values;
• the tooling (if any is used).